System and method for global positioning system enhanced presence rules

ABSTRACT

A telecommunications system includes a plurality of remote clients ( 150 ) including a positioning controller ( 504 ) and a communications controller ( 502 ), the positioning controller receiving position information and the communications controller communicating the position information; and a server ( 152 ) including a coordinating controller ( 161 ) for maintaining a database of location-presence rules for remote clients that are being tracked. The location-presence rules are user-configurable from a network client ( 122 ). In certain embodiments of the present invention, the position information is received from a global positioning system and the communications controller is a cellular telephone controller.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to commonly-assigned, co-pending applicationSer. No. 10/672,456, titled, SYSTEM AND METHOD FOR WEB-BASED PRESENCEPERIMETER RULE MONITORING; application Ser. No. 10/672,105, titled,SYSTEM AND METHOD FOR PRESENCE ALARMING; application Ser. No.10/672,621, titled, SYSTEM AND METHOD FOR SPEED-BASED PRESENCE STATEMODIFICATION; application Ser. No. 10/672,902, titled, SYSTEM AND METHODFOR FAILSAFE PRESENCE MONITORING; application Ser. No. 10/672,439,titled, SYSTEM AND METHOD FOR PRESENCE-BASED AREA MONITORING;application Ser. No. 10/672,641, titled, SYSTEM AND METHOD FOR GLOBALPOSITIONING SYSTEM (GPS) BASED PRESENCE; application Ser. No.10/672,337, titled, SYSTEM AND METHOD FOR IN-BUILDING PRESENCE SYSTEM;application Ser. No. 10/672,367, titled, SYSTEM AND METHOD FORALTERNATIVE PRESENCE REPORTING SYSTEM; application Ser. No. 10/672,057,titled, SYSTEM AND METHOD FOR CENTRALLY-HOSTED PRESENCE REPORTING; andapplication Ser. No. 10/672,364, titled, SYSTEM AND METHOD FOR PRESENCEPERIMETER RULE DOWNLOADING, all filed concurrently on Sep. 26, 2003.

FIELD OF THE INVENTION

The present invention relates to telecommunications systems and, inparticular, to an improved system and method for providing andmaintaining presence information.

BACKGROUND OF THE INVENTION

Presence systems, such as Instant Messaging systems, provide relativelybasic information to network clients concerning the presence status ofrelated users, such as those on the network clients' buddy lists. Intypical operation, a presence status of each user is determined and thatinformation is distributed to those who are watching the correspondinguser.

Even in Internet Protocol (IP) telephone networks, presence status istypically determined using relatively basic presence indications. Theseinclude, for example, detection of whether the user is logged on,detection of keyboard activity, detection of whether a desk phone is inuse or in a do-not-disturb mode, detection of Instant Messagingactivity, or detection of a manual presence setting. Consequently,errors or inaccuracies in presence reporting are relatively common.

For example, suppose a user left the office for lunch and has manuallychanged his presence status to reflect this. He then returns, butforgets to change the status and then leaves on a business trip. Peoplewho check his status will be informed that he is still unavailable,i.e., out to lunch, when it may in fact be possible to reach him at analternative location, such as a cell phone.

As such, there is a need for an improved system and method foraccurately reporting a user's presence status. There is a further needfor a system and method for tracking a user in a presence system.

SUMMARY OF THE INVENTION

These and other drawbacks in the prior art are overcome in large part bya system and method according to embodiments of the present invention.

A telecommunications system according to an embodiment of the presentinvention includes a plurality of remote clients including a positioningcontroller and a communications controller, the positioning controllerreceiving position information and the communications controllercommunicating the position information; and a server including acoordinating controller for maintaining a database of location-presencerules for remote clients that are being tracked. The location-presencerules are user-configurable from a network client. In certainembodiments of the present invention, the position information isreceived from a global positioning system and the communicationscontroller is a cellular telephone controller.

A telecommunications server according to an embodiment of the presentinvention includes a presence control unit adapted to receive andmaintain presence information for a plurality of users; and a locationcontrol unit adapted to receive and maintain location information forthe plurality of users, the location information correlated with thepresence information. The, location information is received from remoteusers having positioning controllers for receiving location informationand communication controllers for transmitting the location informationto said server via a wireless communication network. The presence andlocation correlation rules are received from one or more network clientsoperably coupled to the server and associated with the remote users.

A better understanding of these and other specific embodiments of theinvention is obtained when the following detailed description isconsidered in conjunction with the following drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a telecommunication system according to an embodimentof the present invention;

FIG. 2 is a diagram illustrating an exemplary enterprisetelecommunications server according to an embodiment of the presentinvention;

FIG. 3A-FIG. 3D illustrate exemplary rules setting and mapping graphicaluser interfaces according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating an exemplary remote telecommunicationsserver according to an embodiment of the present invention;

FIG. 5 is a block diagram illustrating an exemplary wirelesstelecommunications device according to an embodiment of the presentinvention;

FIG. 6 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIGS. 7A-7C are flowcharts illustrating operation of embodiments of thepresent invention;

FIGS. 8A-8B are flowcharts illustrating operation of embodiments of thepresent invention;

FIG. 9 is a block diagram illustrating an embodiment of the presentinvention;

FIG. 10A and FIG. 10B illustrate exemplary control e-mails according toembodiments of the present invention;

FIG. 11 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 12 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 13 is a diagram schematically illustrating operation of anembodiment of the present invention;

FIG. 14A and FIG. 14B illustrate exemplary SMS messages according to anembodiment of the present invention;

FIG. 15 is a signaling diagram illustrating operation of an embodimentof the present invention;

FIG. 16A-FIG. 16C illustrate exemplary remote devices according toembodiments of the present invention;

FIG. 17 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 18 is a diagram illustrating an embodiment of the presentinvention;

FIG. 19A-FIG. 19C are flowcharts illustrating operation of embodimentsof the present invention;

FIG. 20A-20B schematically illustrate embodiments of the presentinvention;

FIG. 21 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 22 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 23 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 24 is a diagram illustrating an embodiment of the presentinvention;

FIG. 25 is a diagram illustrating operation of an embodiment of thepresent invention;

FIG. 26 is a diagram illustrating an embodiment of the presentinvention;

FIG. 27 is a diagram illustrating a graphical user interface accordingto an embodiment of the present invention;

FIG. 28 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 29 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 30 is a diagram illustrating an embodiment of the presentinvention;

FIG. 31 is a diagram illustrating an embodiment of the presentinvention;

FIG. 32 is a flowchart illustrating operation of an embodiment of thepresent invention;

FIG. 33 is a diagram illustrating operation of an embodiment of thepresent invention;

FIG. 34 is a diagram illustrating operation of an embodiment of thepresent invention;

FIG. 35 is a flowchart illustrating operation of an embodiment of thepresent invention; and

FIG. 36 is a flowchart illustrating operation of an embodiment of thepresent invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

System Overview and User Interface

Turning now to the drawings and, with particular attention to FIG. 1, adiagram of an exemplary telecommunications system 1000 according to anembodiment of the present invention is shown. As shown, thetelecommunications system 1000 includes an enterprise network 1002, awireless communication network 1004, and may also include a globalpositioning network 1006.

The wireless communication network 1004 may be implemented as any of avariety of wireless telecommunications networks, such as a personalcommunication service (PCS) or cellular-type network, including dial-upcellular, or data cellular networks such as CDPD networks, SMS networks,WiFi networks, and the like. In other embodiments, the wirelesscommunications network 1004 may be implemented as one or more two-wayradio networks. The wireless communication network 1104 includes one ormore network clients implemented as wireless devices 150, also referredto as remote devices. The wireless devices 150 may include positioningcontrollers 504 and communication controllers 502. As will be explainedin greater detail below, the positioning controller 504 is configured toDetermine position or location of the wireless device 150, such as byreceiving global positioning network signals from one or more globalpositioning satellites 1006. It is noted, however, that any mechanism tolocate the device within the desired degree of precision may beemployed. As will be explained in greater detail below, the remotedevice 150 operates to receive location information from the positioningsystem and transmit location and/or presence updates to one or moreusers or servers using the communication controllers. The remote device150 may likewise receive presence and/or program updates from theservers. In certain embodiments, the communication controllers 502 arecellular telephone controllers.

In certain embodiments of the present invention, the wireless network1004 includes one or more positioning or remote servers 152. As will beexplained in greater detail below, the remote server 152 may include acoordinating controller including a remote location control unit (RLCU)162 and a remote presence control unit (RPCU) 164. The remote locationcontrol unit 162 may interact with an interface 166 to receive locationsignals from the remote users 150 and transmit updates, typicallyreceived from the enterprise network 1002, to the remote users 150. Incertain embodiments, the interface 166 is implemented as a telephonedial-up interface. The remote presence control unit 164 may interactwith an interface 168 for transmitting and receiving presence and/orlocation related updates to the enterprise server 104. Presence and/orlocation rules, such as user identification and correlation pairs, maybe stored in database 107.

As noted above, in the embodiment illustrated, the telecommunicationssystem 1000 of FIG. 1 includes an enterprise network 1002. As shown, theenterprise network 1002 includes a local area network (LAN) 102. The LAN102 may be implemented using a TCP/IP network and may implement voice ormultimedia over IP using, for example, the Session Initiation Protocol(SIP) or ITU Recommendation H.323. Coupled to the local area network 102is an enterprise or presence server 104, which may be embodied as amultimedia server including a presence server or service.

The server 104 may include one or more controllers 101, which may beembodied as one or more microprocessors, and memory 103 for storingapplication programs and data. As will be explained in greater detailbelow, the server 104 may provide a variety of services to variousassociated client devices, including telephones, personal digitalassistants, text messaging units, and the like. Further, according toembodiments of the present invention, the controllers 101 may implementan interactive suite of applications 112, including enterprise presencecontrol units and enterprise location control units, as will beexplained in greater detail below.

Also coupled to the LAN 102 is a gateway 116 which may be implemented asa gateway to a private branch exchange (PBX), the public switchedtelephone network (PSTN) 117, or any of a variety of other networks,such as a wireless, PCS, or cellular network. In addition, one or morelocal controllers such as LAN or IP telephones 120 a-120 n and one ormore computers 122 a-122 n may be operably coupled to the LAN 102. Aplurality of cellular telephone units 150 may also couple to thenetwork, via gateway 116.

The computers 122 a-122 n may be personal computers implementing theWindows XP operating system and thus, running Windows Messenger client.In addition, the computers 122 a-122 n may include telephony and othermultimedia messaging capabilities using, for example, peripheralcameras, microphones and speakers (not shown) or peripheral telephonyhandsets. In other embodiments, one or more of the computers may beimplemented as wireless telephones, digital telephones, or personaldigital assistants (PDAs). Thus, the figures are exemplary only. Thecomputers may include one or more Pentium-type microprocessors, andstorage for applications and other programs. The computers may furtherimplement network interface devices 124 for presence control and networkinteraction and receiving signals for transmission over the network tothe server 104.

In operation, a user may use one of the computers 122 to upload a set ofone or more location-presence correlation rules to the enterprisepresence server 104. The enterprise presence server 104 then maintains adatabase in memory 103 of presence users and their location rules. Thisinformation can then be provided when users' watch lists are updated, aswill be explained in greater detail below. In turn, the enterpriseserver 104 can upload the rules to the remote location server 152.These, in turn, can be transmitted to the appropriate remote device 150,for example, via a dial-up operation. When the remote device 150 thenreceives location information from the GPS system 1006, it can contactthe remote server 152 and transmit the corresponding location and/orpresence information. The remote server 152 ill then distribute theinformation to the appropriate local server 104, which ill update thepresence databases and watch lists for the various users.

Turning now to FIG. 2, a functional model diagram illustrating a server104 including a control unit 114 is shown. More particularly, FIG. 2 isa logical diagram illustrating a particular embodiment of a server 104.The server 104 includes a plurality of application modules 112 and acommunication broker module 201. In addition, the server 104 providesinterfaces, such as SIP APIs (application programming interfaces) 220 toSIP IP phones 221 and gateways/interworking units 222.

According to the embodiment illustrated, the broker module 201 includesa basic services module 214, presence module 215, an advanced servicesmodule 216, and a toolkit module 218.

The basic services module 214 functions to implement, for example, phonesupport, PBX interfaces, call features and management, as well asWindows Messaging and RTC add-ins, when necessary. The phone supportfeatures allow maintenance of and access to buddy lists and providepresence status.

It is noted that the above are MS Windows related terminology, but thisinvention can work in any type of IP based network, such as IBMSameTime, SUN One and the like.

The advanced services module 216 implements functions such as multipointcontrol unit (MCU), recording, Interactive Voice Response (IVR), and thelike. MCU functions are used for voice conferencing and support ad hocand dynamic conference creation from a buddy list following the SIPconferencing model for ad hoc conferences. In certain embodiments,support for G.711 and G.723.1 codecs is provided. Further, in certainembodiments, the MCU can distribute media processing over multiple MC's(Multimedia Processors) servers using the MEGACO protocol.

Presence features 215 provide device context for both SIP registereddevices and user-defined non-SIP devices. Various user contexts, such asIn Meeting, On Vacation, In the Office, etc., can be provided for. Inaddition, voice, e-mail and instant messaging availability may beprovided across the user's devices. The presence feature 215 enablesreal time call control using presence information, e.g., to choose adestination based on the presence of a user's devices. In addition,various components have a central repository for presence informationand for changing and querying presence information. In addition, thepresence module 215 provides a user interface for presenting the userwith presence information.

The broker module 201 may include an interactive voice response (IVR)such as the ComResponse platform, available from Siemens Information andCommunication Networks, Inc. ComResponse features include speechrecognition, speech-to-text, and text-to-speech, and allow for creationof scripts for applications.

In addition, real time call control is provided by a SIP API 220associated with the basic services module 214. That is, calls can beintercepted in progress and real time actions performed on them,including directing those calls to alternate destinations based on rulesand or other stimuli. The SIP API 220 also provides call progressmonitoring capabilities and for reporting status of such calls tointerested applications. The SIP API 220 also provides for call controlfrom the user interface.

According to the embodiment illustrated, the application modules 112include a collaboration module 202, an interaction center module 204, amobility module 206, an interworking services module 208, and apresence-location control module 114.

The collaboration module 202 allows for creation, modification ordeletion of a collaboration session for a group of users. Thecollaboration module 202 may further allow for invoking a voiceconference from any client. In addition, the collaboration module 202can launch a multi-media conferencing package, such as the WebExpackage. It is noted that the multi-media conferencing can be handled byother products.

The interaction center 204 provides a telephony interface for bothsubscribers and guests. Subscriber access functions include calendaraccess and voicemail and e-mail access. The calendar access allows thesubscriber to accept, decline, or modify appointments, as well as blockout particular times. The voicemail and e-mail access allows thesubscriber to access and sort messages.

Similarly, the guest access feature allows the guest access to voicemailfor leaving messages and calendar functions for scheduling, canceling,and modifying appointments with subscribers. Further, the guest accessfeature allows a guest user to access specific data meant for them,e.g., receiving e-mail and fax back, etc.

The mobility module 206 provides for message forwarding and “one number”access across media, and message “morphing” across media for thesubscriber. Further, various applications can send notification messagesto a variety of destinations, such as e-mails, instant messages, pagers,and the like. In addition, the subscriber can set rules that themobility module 206 uses to define media handling, such as e-mail, voiceand instant messaging handling. Such rules specify data and associatedactions. For example, a rule could be defined to say “If I'm traveling,and I get a voicemail or e-mail marked Urgent, then page me.”

The presence-location control module 114 may include database controller223, a location control unit 217 and a location-presence control unit219. As will be described in greater detail below, the databasecontroller 223 operates to supervise network users, theirlocation-presence rules, and their watch lists. The location controlunit 217 may operate to receive location information from the remoteserver 152 or directly from users 150. The location-presence controlunit 219 operates in conjunction with the presence unit 215 and thedatabase controller 116 to receive and maintain the presence and/orlocation rules for the corresponding users.

As noted above, the computers 122 may include interfaces 124 forinputting inbound and outbound location-presence rules and presenceinformation. Such rules define both the user's availability (presence)and a specific location associated with the availability. The user canalso specify callers who are allowed particularized access to the user.FIG. 3A-3D illustrate exemplary interfaces that may be used to setlocation and presence rules. It is noted that the specific rules andlocations described are exemplary only.

As shown in FIG. 3A, in the embodiment illustrated, the user can setlocation 3900, availability 3902, callers 3904, and status 3906. It isnoted that while particular examples are shown, other locations,availability, callers, and status may be specified. In addition, incertain embodiments, day of week and time of day parameters may also bespecified. Thus, the figures are exemplary only.

As shown, example locations 3900 include Exact Address 1 (Office); ExactAddress 2 (Home); On Campus; Within City (Radius 1); Outside City(Radius 2); and Within City (Traveling). “Exact addresses” allow theuser to specify the exact address of a building or location and set arule if the user is within a predetermined distance of the location. “Oncampus” allows the user to specify a rule if the user is on, e.g., thecorporate campus. “Within city or outside radius 1” allows the user tospecify a rule for when he is outside the campus or a specifiedbuilding, but within a home city. “Outside city or outside radius 2”allows the user to set a rule for when he is outside the home city or aparticular radius. “Within City (Traveling” allows a user to specifythat he is within the radius, but may have limited availability.

Example availability 3902 includes Office Phone, E-mail, InstantMessaging, PDA wireless, Cell Phone, PCS cell phone, S49 cell phone, GSMS49 cell phone, and voicemail. The user's availability thus defines themedium to which the call is forwarded or otherwise handled. As can beappreciated, the availability can depend on the user's location.Further, the user may be available via more than one mediumconcurrently.

Exemplary caller lists 3904 include All Callers; Work Group; orIndividual Callers. Using “All Callers,” the user can specify rules thatwill be binding on everyone who calls. “Work Group” is representative ofone or more specified lists of users; for example, Family could beanother group. “Individual Callers” allow the user to specify a rule toapply on an individual basis to particular callers.

Finally, exemplary presence status 3906 includes At Lunch, At desk,Online, On vacation, In Car, and the like. The status can be set to beautomatically updated when a user is at a particular location, or theuser can manually set it, as will be explained in greater detail below.

Exemplary rules that can be set include:

-   -   1. “While I am in the office <exact address> I am available on        my <office phone>, <e-mail>, and <Instant Messaging>.    -   2. While I am outside of my office <exact location>, but still        <on campus>, I am available on my <PDA wireless> and on my <cell        phone>.    -   3. While I am <one mile> away from <exact address> but still        <within city> I am available on the <PCS phone>.    -   4. While I am more that <50 miles> away from <exact address> I        am available on my <Siemens S49 cell phone>.    -   5. While I am in <Munich> then if the call is from <John> then        dial my <GSM S49 phone>, otherwise forward call to my        <voicemail>.

In addition to user location, presence status rules may be based on theability of GPS systems to track user speed. For example, in certainembodiments, the system can detect that the user is traveling at apredetermined speed and then update his presence status and availabilityto indicate, for example, that his status is “In Car” and that hisavailability is “car phone”, “cell phone,” “not available,” or the like.

For example, as shown in FIG. 3A, the user can set location and the usercan additionally set presence status 3906 to indicate “In Car” when thesystem detects he is traveling above a certain speed, such as 15 milesper hour, for example. The corresponding location 3900 could indicatethat the user is “In City” and “Traveling,” if it is not desired to givea precise street location. Thus, an exemplary presence rule could be

-   -   6. If I am traveling in a speed greater than <15> mph, then I am        in my car—set the presence status to “In my car” and I am then        available at <cell phone>.

FIG. 3B-FIG. 3D illustrate exemplary user interfaces for setting therules. Briefly, such graphical user interfaces include a mapping engine,such as Microsoft MapPoint™, and one or more drop down or sub-menus fordesignating presence and location definitions.

For example, as shown in FIG. 3B, a user can type in an address 301,which will then cause a map to be generated with the location 304highlighted. As can be appreciated, the map of the interface of FIG. 3Bmay represent an office campus, with the location 304 representative ofthe user's office building. The user can then select one of the dropdown menus 306, 308 to set the contact information. For example, menu306 may be used to set Office Phone, IM, or E-mail, typically associatedwith the user's office. Similarly, if outside the address, e.g., atlocation 302, or in another building, e.g., location 310, the user canalso select contact information. Similar drop-down menus can be used toset user speed, etc.

As shown in FIG. 3C, the user may also select a map location 311 and aradius or other boundary 312 around it. The user can then select a modeof contact within or outside the perimeter. For example, the user maytravel from California 314 to Germany 316. Using menus 315, 317, theuser can set the contact type as well as the specific callers who areauthorized to reach him in Germany.

In addition to setting location rules, the user can set associatedstatus rules, as shown in FIG. 3D. For example, the user can designatewhether he is In Office, Working Remotely, etc., and set correspondingcontact information.

Turning now to FIG. 4, a block diagram illustrating an exemplary remoteor positioning server 152 according to an embodiment of the presentinvention is shown. As shown, the remote server 152 includes a controlunit 161, which may include a remote location control unit 162 and aremote presence control unit 164; a message generator 160; a database107 that may include a rules database 402 and a presence-locationdatabase 404; a wireless interface 168; and a network interface 166.

In certain embodiments, the rules database 402 stores location-presencerule pairs for registered users and is accessible by the presencecontrol unit 164 and location control unit 162. Similarly, in certainembodiments, the presence-location database 404 receives the actuallocation information and correlates it with the appropriate rules in therules database 402. In other embodiments, the remote location server 152maintains a database only of remote users and their associatedenterprises. The location and/or presence information received from theremote users is then transmitted to the enterprise server 104.

The wireless interface 166 allows the server 152 to communicate over thewireless network 1004 (FIG. 1) to the remote devices 150. For example,the remote positioning server 152 can transmit rules updates or otherinformation, such as macros, to the remote devices, and can receivepresence updates and other information from them. In certainembodiments, the wireless interface 166 is a dial-up cellular telephoneor PCS interface. For example, the wireless interface 166 may beimplemented as a toll-free dial in for all remote units associated witha particular enterprise.

The message generator 160 and network interface 168 allow communicationwith the enterprise server 104. More particularly, the message generator160 may be embodied as an e-mail message generator for formattingpresence and/or location information into an e-mail for transmission todesignated enterprise users. Similarly, the message generator 160 can beused to unformat or read received messages. In other embodiments, themessage generator may implement text messaging, such as InstantMessaging or SMS messaging.

In operation, as will be explained in greater detail below, the remotepositioning server 152 can receive messages from the enterprise presenceserver 104 via the network interface 168 and in a format readable by themessage generator 160. These messages can include rules and presenceupdates from enterprise users 122. Presence updates can be stored by thepresence control unit 164 in presence-location database 404. Rulesupdates can be stored by the presence control unit 164 in the rulesdatabase 402. Presence and/or rules updates can then be transmitted bythe presence control unit 164 to remote users 150 using the wirelessinterface 166.

Similarly, location updates from remote users 150 can be received by thelocation control unit 162 via the wireless interface 166. The locationcontrol unit 162 can then store the new location information in thepresence-location database 404. The presence control unit 164 can thentransmit the new location and/or presence information to the enterpriseserver 104 using the message generator 160, as discussed above.

It is noted that, in certain embodiments, the enterprise server and theremote server may be the same unit and provided with dial in capabilityfrom the remote devices. Thus, the figures are exemplary only.

Turning now to FIG. 5, a block diagram of an exemplarytelecommunications device 150 according to an embodiment of the presentinvention is shown. As noted, above, the device 150 may be compatiblewith any of a variety of PCS or cellular-type networks, including, forexample, GSM, and 2G, 2.5G, and 3G cellular telephone systems. In theembodiment illustrated, the remote unit 150 includes a wirelesscontroller 502, such as a cell phone or radio data network controller,and a GPS receiver 504, for receiving location or positioning signals.In addition, the remote unit 150 may maintain a rule database 506 oflocation-presence rules, and a rules compare controller 508 forcomparing current conditions to those specified in the rules. As will beexplained in greater detail below, the remote device 150 can send thelocation server 152 an update of location or presence information. Theremote device 150 can likewise receive software and rules updates fromthe enterprise and/or presence severs.

Turning now to FIG. 6, a flowchart illustrating operation of anembodiment of the present invention is shown. In particular, theflowchart of FIG. 6 illustrates setting one or more location-presencerules. Initially, at step 602, the user can set one or morelocation-presence rules using his enterprise computer 122 and mappinginterface 124. At step 604, the user can transmit the rules from hisenterprise computer 122 to the enterprise presence server 104. Theenterprise server 104's location-presence control unit 219 may thenstore the rules in the database 116. If the enterprise-presence server104 does not actively maintain the tracking, the enterprise-presenceserver 104 will transmit the rules to the remote location server 152, atstep 606. For example, the remote location server 152 may maintain adedicated dial up or Internet connection for receiving the rules fromenterprise users via interface 168 (FIG. 4). At step 608, the remotelocation server 152's control unit 161 stores the rules in itspresence-location database 404. Depending on how network and devicepositioning functionality is configured, the remote location server 152may then transmit the rules to the user remote device 150 at step 610.For example, the remote location server 152 may dial up the remotedevice's telephone number; when the call is answered, the informationcan be uploaded. The user remote device 150 may be at least partiallyresponsible for resolving location and presence correlations anddetermining when updates to status need to be made. Alternatively, theremote location server 152 could be solely responsible and thus need nottransmit the rules to the remote user device 150, though a signalindicating the user device 150 should begin location monitoring may besent. In either case, at step 612, the remote user device 150 willmonitor the device location.

Turning now to FIG. 7A, a flowchart illustrating device monitoring ofdevice position according to an embodiment of the present invention isshown. At a step 702, the remote device 150 receives positioninformation via its position receiver 504 (FIG. 5). As noted, above, theposition receiver 504 may be adapted to receive one or more positionsignals from a global positioning network 1006 (FIG. 1). At step 704,the remote user device 150 uses its location compare unit 508 to accessthe rules database 506. At step 706, the location compare unit 508determines if there has been a location or presence change. If so, thenat step 708, the wireless control unit 502 sets up a call to theappropriate server 152, 104 to advise of the new condition. It is notedthat in other embodiments, the remote unit 150 can simply forward anyreceived location or position information to the server as soon as it isreceived, without performing analysis or compares on the receivedinformation.

FIG. 7B illustrates more particularly location monitoring and updatingaccording to an embodiment of the present invention. In particular, FIG.7B illustrates the remote device 150 performing location-rules comparesaccording to embodiments of the present invention. At a step 720, theremote device 150 receives position information via its positionreceiver 504. As noted above, the position receiver 504 may be adaptedto receive one or more position signals from a global positioningnetwork, such as the GPS network 1006. At step 722, the remote device150 uses its location rule compare unit 508 to access the rules database506 and perform a location compare, to determine if there has been alocation and/or presence change. If there has been no change, asdetermined at step 724, then monitoring continues, at step 726.Otherwise, at step 728, the wireless controller 502 transmits theupdates to the remote location server 152. For example, the remote unit152 could dial a toll-free number at the server 152. The updateinformation can be location update or presence status update, or both.The remote location server 152 updates the device's position and/orpresence information in its presence-location database 404 and contactsthe enterprise server 104 at step 730. For example, the control unit 161may cause the message generator 160 to generate a control e-mail messagewith the update and transmit it via the interface 168. Alternatively,the remote server 152 could simply dial in to a toll free number at theenterprise server 104 to deliver the information. The enterprise server104 then receives the update, translates the message, updates itsdatabase 116, and distributes the updates to the watching parties atstep 732. Calls to the user whose position is being tracked can then beforwarded according to the location-presence rules. As noted above, thiscan include forwarding to one or more telephony or messaging devices.

FIG. 7C illustrates an alternate embodiment of the present invention. Inparticular, in FIG. 7C, the remote device 150 merely transmits locationinformation to the remote server, which then performs thelocation-presence rules check(s). At a step 740, the remote device 150receives position information via its position receiver 504. As noted,above, the position receiver 504 may be adapted to receive one or moreposition signals from a global positioning network 1006. At step 742,the wireless control unit 502 contacts the remote server 152 andtransmits the received coordinates or position information. At step 744,the remote server 152's control unit 161 stores the information at thepresence-location database 404 and accesses the rules database 402 todetermine if the user's location has changed. If it has, then themessage generator 160 composes a message including the updateinformation, which is sent to the enterprise presence server 104. Asnoted above, the message may be an e-mail message. Alternatively, themessage may be in a format similar to that received from the remote unitand the communication is via a telephone dial up. At step 750, theenterprise server 104 then updates its database 116 and provides thenewly updated presence information to other enterprise and remote users,as necessary. Calls to the user whose position is being tracked can thenbe forwarded according to the location-presence rules. If, in step 746,there was no location change, the system would simply continue tomonitor, in step 752.

In the embodiments discussed above, the location and/or presenceinformation is provided to the enterprise via a remote server 152. Theremote server can be provided by a cellular service provider, forexample. Each enterprise can be associated with a toll free number atthe remote server and transmits the positioning data by calling thisnumber. The remote server then uses its message generator to generate,for example, an e-mail message to the enterprise server. It is notedthat, in other embodiments, the generated message could be a textmessage such as an IM message or an SMS message. Alternatively, theenterprise server could also be equipped with a dedicated phone line forreceiving the information.

This is generally illustrated with reference to the flowchart of FIG.8A. As shown in FIG. 8A, once the remote unit 150 receives the locationinformation, in step 802, it can contact the remote server 152 via atoll-free dial up, for example, through the cellular and/or publicswitched telephone networks. At step 804, the remote server, 152, whichmay be a service provided by the cellular or PCS service provider,receives the location and/or presence update. At step 806, the remoteserver 152 formats the received information into an appropriate format,e.g., an e-mail format, and transmits it to the enterprise server 104.The enterprise server 104 receives it and updates the presenceinformation, as discussed above, in step 808.

In the alternative, as shown in FIG. 8B, the function of the remoteserver and the enterprise server could be combined in a single unit atthe enterprise site. In this case, the enterprise server 104 would beprovided with an interface for receiving calls from the remote devices.For example, a modem card could be provided, with a dial in. In thiscase, as shown at step 820, the remote device 150 calls the enterprisenumber with location and/or presence updates. At step 822, theenterprise server 104 receives the updates and distributes them torequesting parties on the network, e.g., as a SIP message, at step 824,in manner similar to that discussed above.

Service Provider Central Server

As noted above, according to embodiments of the present invention, thevarious of the presence and location server functions may be provided byeither the enterprise or the service provider. FIGS. 9-12 illustrate ingreater detail an embodiment in which location-presence services areprovided by a remote cellular service provider.

For example, as shown in FIG. 9, presence server is shown which may beimplemented as a centrally-hosted function by a service provider as aservice to customers. In the embodiment illustrated, status updates arereceived via a dedicated toll free number and then provided toenterprise devices via e-mail or text messages. Similarly, programupdates may be received as e-mail or text messages and then transmittedto the remote devices.

In FIG. 9, a server 900 is shown. The server 900 includes a telephoneinterface 166, a control unit 161, a party-rules database 402, and apresence message generator 160. The telephone interface 166 may be atelephone interface, such as a modem, accessible via a dedicatedtoll-free number for each enterprise. Also shown is an exemplaryenterprise client computer 122.

In operation, when the remote device 150 has a presence status update totransmit to an enterprise client, the remote device 150 dials in to thetoll-free number and transmits the information to the server 900. Thecontrol unit 161 then accesses the rules database 402 and the presencemessage generator 160 generates a message 902 to the enterprisecontaining the status update. The message may be in a variety offormats. For example, the message may be in an e-mail format, or a textmassage format such as an SMS format, an IM format, and the like. Thestatus e-mail may be directed to either a particular network client 122or to the enterprise server 104. If it is directed to a particularnetwork client, the enterprise server or the gateway will simply forwardthe message to the one or more network clients. Otherwise, the messagemay be directed to the enterprise server; the enterprise server can thenread the message and use the information to update watch lists andpresence status, etc.

As noted above, the enterprise and the remote server can shire variousof the presence-location responsibilities. For example, in oneembodiment, the remote server 900 can handle all location-presencefunctions. In this case, the database 402 includes not only party rules,but also the presence status; this information is transmitted in thee-mail updates to the enterprise site. Alternatively, the remote server900 could merely form a conduit for location information and sendlocation updates to the enterprise according to the rules database. Theenterprise server then updates the presence information.

Similarly, the enterprise client computer 122 may also compose a messagesuch as an e-mail message including, for example, program updates orrule updates for transmission to the remote server 900. The update canbe either in the body of the e-mail or as an attachment. The e-mailmessage is received at the remote server 900. The remote server 900 thenidentifies the sender and recipient; and reads the e-mail. If the e-mailcontains a rules update, then the database 402 is updated. The remotedevice may also be called via the interface 166 and the update uploadedto the device. A program update is handled similarly.

Turning now to FIG. 10A and FIG. 10B, diagrams of exemplary updatee-mails according to embodiments of the present invention are shown.Shown in FIG. 10A is an exemplary presence update e-mail 1002. Thepresence update e-mail 1002 is generated by the message generator 160 toprovide the update to the enterprise clients 122.

In the embodiment illustrated, a subject line 1004 identifies themessage as a presence update message. The body of the message caninclude party status 1006 and recipients 1008. Alternatively, the TO:line can identify the parties who shall receive the update.

Similarly, FIG. 10B illustrates an exemplary rules update e-mail message1010. The rules update e-mail message can be generated at the client 122and transmitted to a predetermined e-mail address associated with theserver 900. The message 1010 may include a subject header 1012identifying the message as a rules update message, while the body 1014may contain the actual update content.

FIG. 11 is a flowchart illustrating operation of an embodiment of thepresent invention. In particular, FIG. 11 illustrates transmission ofpresence updates according to an embodiment of the present invention. Atstep 1102, the remote unit 150 has a status change, i.e., detects achange in position. At 1104, the remote unit 150 signals the remoteserver with the change. For example, the remote unit 150 can dial atoll-free number to establish a telephone or data connection viainterface 166. At 1106, the remote server 900's presence control unit162 updates the presence database with the presence information. At step1108, the remote server 900's presence message generator 160 is used togenerate an e-mail or other message for the enterprise. At step 1110,the enterprise receives the update and it is distributed to theappropriate parties. As noted above, the e-mail may be addressed toindividual parties or to a central enterprise server which thendistributes its contents.

Turning now to FIG. 12, a flowchart illustrating rules updatingaccording to an embodiment of the present invention is shown. At step1202, the enterprise client user 122 updates his presence rules. Forexample, as discussed above, the user may input one or more ruleschanges into his computer or other network device. At step 1204, theupdate contents are sent as an e-mail to the remote server 900. At step1206, the remote server 900 receives the contents and updates itsdatabase. At step 1208, the rules updates may be provided to the remoteunit.

Interfacing to the Remote Device

As discussed above, according to embodiments of the present invention,presence-position and software updates may be transmitted to and fromthe remote device via a cellular telephone dial-up. That is, to reportchanges in position, the remote device 150 may dial a toll free numberassociated with either the remote or enterprise server and using a modem(or similar device on a digital channel), transmit the positioninformation on the voice channel. However, other cellular datatechnologies may be used. In other embodiments of the invention, anyradio data network may be used, such as the cellular control channel(e.g., using SMS or CDPD technologies); wireless LAN technologies (e.g.,Wi-Fi or IEEE 802.11a, b, g); or two-way radio technologies may beemployed for sending and receiving the presence or update information.

In FIGS. 13-15, operation of such embodiments will be discussed withreference to an SMS-based system. In particular, FIG. 13 illustrates anexemplary network configuration for such an embodiment. FIG. 13illustrates a system in which a data communications network such as aShort Message Service (SMS) is used for position and software updatetransmission. As noted above, other data transmission systems may beemployed, however.

Shown are a remote device 150 and a server 152. Also shown are awireless network 1302, an SMSC 1300, and Internet/Intranet 1304. As willbe explained in greater detail below, the remote device 150 receivespositioning signals (not shown) from a positioning network and transmitsthem via the wireless network 1302 to the SMSC 1300. The SMSC 1300 thentransmits the message over Internet/Intranet 1304 to the server 152.

In the embodiment illustrated, the remote device 150 includes GPSreceiver 504, cellular transceiver 502, and a data interface 159, suchas an e-mail or text messaging interface. As illustrated, the interfaceis particularly SMS control unit 159. Similarly, remote server 152includes interface 166, which is an interface for receiving the SMSmessages via Internet/Intranet 1304. Similarly, the remote server 152can send updates to the remote device 150 as SMS messages.

Exemplary SMS messages are shown in FIG. 14A and FIG. 14B. It is notedthat such messages may be embodied as text or data messages. Shown inFIG. 14A is an exemplary SMS status message 1400. As discussed above,such a status message may be received from the remote unit 150. Asshown, a status SMS message 1400 can include an identifier 1402identifying the message as a position status message; a deviceidentification 1404 identifying the transmitting device; and thecorresponding position information 1406. Similarly, a rules updatemessage is shown in FIG. 14B. The rules update message is sent from theremote server 152 to the remote device 150 to update thepresence/location rules. As shown, the message includes an updateidentifier 1408 identifying the message as an update message; a deviceidentifier identifying the destination device; and the updateinformation 1414.

Operation of an embodiment of the present invention is shown withreference to the signaling diagram of FIG. 15. Shown are remote device150, SMSC 1300, Remote Server 152, and Enterprise Server 104. It isnoted that other network configurations are possible. Thus, the figureis exemplary only. Shown at 1500 is the remote device 150 receiving GPSsignals and transmitting corresponding information to the enterpriseserver 104. Transmission of software/firmware updates to the remotedevice 150 is shown at 1502.

At 1504, the remote device 150 receives one or more position signals,i.e., GPS position signals. The SMS controller 159 receives positionand/or presence signals from the GPS receiver 156, and converts theminto the proper SMS message format at 1506, as discussed, for example,with reference to FIG. 13. The SMS controller 159 then dials theappropriate contact number at the remote server 152, at 1508. The SMSmessage travels on the cellular control channel to the SMSC 1300, whichthen forwards it to the remote server 152, at 1310. The remote server152 may then pass the message on to the enterprise server 104, at 1512.As discussed above, the remote server 152 may transmit the informationas an e-mail or other message. The enterprise server 104 may thenprocess and distribute the presence information accordingly.

Transmission of updates to the remote device 150 is shown at 1502. At1514, the enterprise server 104 receives one or more program updates orlocation rule updates from the network client (FIG. 1). The enterpriseserver 104 can receive the updates, for example, in a network formatsuch as SIP format. Once received, the enterprise server 104 transmitsthe update to the remote server 152, at 1516. At 1518, the remote server152 converts the received update into a network transmission format,such as SMS format. At 1520, the remote server 152 dials the remotedevice cell number and transmits the SMS message over the cellularcontrol channel to the SMSC 11300, which then forwards it to the remotedevice 150.

Remote-Device Based Compare

As noted above, the remote device 150 may itself receive rules updatesfrom network clients via the remote server 152. In certain embodiments,the remote device 150 may also perform the location and/or presencecompare operations. In such embodiments, the remote device 150 may thenneed to signal the remote server 152 only when a change in statusoccurs, such as the remote unit leaving a location defined by aperimeter, boundary, range, or presence rule defined by the user.

Remote device based compare units are shown schematically with referenceto FIGS. 16A-16C. Shown in FIG. 16A is an exemplary location rulescompare unit 508 that functions to identify if there has been an updatein the user's current location. The unit 508 includes a comparator 1602that receives as inputs a current location 1804 and a previous location1606. In operation, the remote unit 150 receives the location signalscorresponding to the current location and input them to the comparator1602. The remote device 150 also accesses memory (not shown) for theprevious location, which is also sent to the comparator 1602. Thecomparator 1602 determines if there has been a significant change in theuser's location from the previous location. If so, the comparator 1602may output a signal 1608 directing the remote device 150 to transmit tothe remote server 152. Otherwise, no action is taken.

FIG. 16B illustrates another exemplary location rule compare unit 508.In the embodiment illustrated, the unit 508 compares the location and arule and outputs to the presence unit if there is a change. Thus, asshown in FIG. 16B, the location rules compare unit 508 includescomparator 1602 receiving current location 1604 and previous location1606 inputs. The comparator 1602 functions as described with referenceto FIG. 18A, and provides an output 1608 representative of whether therehas been a change in position. The signal 1608 is provided to acomparator 1610. The other input to the comparator 1612 is a geographicrule 1612 from the rules database 506. The comparator 1610 then providesan output 1614 representative of whether there has been a change to ageographic rule. This signal may then be provided to the remote server.Alternatively, the output 1614 may be provided to the databasecontroller 506 to determine if there is an associated presence update.If so, this will be provided to the remote server, at 1616.

As noted above, either the location or presence may trigger an updatesignal to the remote server. FIG. 16C illustrates an embodiment in whicha presence update triggers a signal to the remote server. As shown, thecurrent location 1604 is input to the rules database 506. The rulesdatabase 506 accesses the current presence rule and outputs it at 1618.The current presence state is input to comparator 1620, as is theprevious presence rule 1622.

FIG. 17 is a flowchart illustrating operation of embodiments of thepresent invention. At a step 1702, the remote device 150 receivespresence-location rules. As described above, the remote device 150 canreceive the rules as a cellular data call. The updated rules are thenstored in the rules database 506.

At a step 1704, the remote device 150 begins to monitor its currentlocation, such as by receiving global positioning signals. At a step1706, the remote device 150's location rule compare unit 508 willcompare the received location to the corresponding location rule storedin the database 506. If there is not change, as determined in a step1708, then the remote device 150 will simply continue to monitor thelocation. If, however, there is a location change, then differentactions may occur, depending on the embodiment.

In one embodiment, in a step 1710, the location change is transmitted tothe remote server or the enterprise server, which then process theinformation. Alternatively, in a step 1712, the location rule compareunit 508 can access the rules database 506 for the correspondingpresence status rule and determine the current presence state. Incertain embodiments, at a step 1716, the remote device 150 will thentransmit the accessed current state to the remote or enterprise server.In other embodiments, in a step 1714, the location rules compare unit508 will determine if there has been a change in the presence state. Ifso, then in a step 1718, this change, or the new presence state, will betransmitted to the remote or enterprise server. If there has been nostate change, then the system continues to monitor location and presenceat step 1704.

It is noted that in certain embodiments, the current location may beused to determine whether there has been a presence change, withoutmaking an explicit determination of whether there has been a locationchange. Thus, after step 1706, the system could proceed to step 1712,without an intervening step 1708.

Watchdog Timer

In certain embodiments of the present invention, either or both of theremote units and the server(s) may be provided with a watchdog timer toallow for confirmation the remote units are still running.

Shown in FIG. 20 is an exemplary server, such as enterprise server 104or remote server 152, and a remote user device 150. The remote device150 may be provided with a watchdog timer 1804, or the server 152 may beprovided with a timer 1802. At periodic intervals, the remote device 150and remote server 152 may communicate timer ticks with one another, forexample, by calling the toll-free or user device telephone numbers.

In one embodiment, the remote unit 150's timer 1804 maintains apredetermined count; when the timer expires, the remote unit 150 sends acurrent location and/or presence or status change to the remote server152. Thus, the remote unit 150 sends location and/or presence updates tothe remote server 152 on a periodic basis.

In another embodiment, the remote server 152's timer 1802 maintains acount when a user device 150 is detected. Upon expiration of the timer,the server 152 sends a “here I am” signal to the remote user, requestingthat it send a location and/or presence update; alternatively, the “hereI am” signal could merely indicate that the remote unit 150 should senda response tick, until an actual location or presence change occurs, atwhich point the remote unit 150 sends the updates. Such timer ticksignals may be sent, for example, on cellular control channels. If theremote server 152 does not receive a response to its timer tick, it canupdate the corresponding remote unit's presence status to “unknown” or“unavailable” or otherwise indicate that the remote user has notresponded to the timer tick status request.

FIG. 19A is a flowchart illustrating operation of an embodiment of thepresent invention. In particular, as shown, the remote device isprovided with a timer and periodically sends updates to the remoteserver 152. As shown, at a step 1902, the remote device 150 activates orotherwise registers with the remote server 152 and begins monitoringlocation and/or presence status. For example, in the case of a cellphone, the device 150 detects and registers with a base station (notshown) in a known manner and can then send an initial location-presenceindication to the remote server 152 in a manner similar to thatdescribed above. At a step 1904, the remote device 150 can activate itstimer 1804. At a step 1906, the remote device 150 may determine that itslocation and/or presence status has changed. If so, then in step 1910,the remote device 150 will transmit the change to the remote server 152,and the timer 1804 will be reset. Otherwise, in step 1908, the timer1804 will expire, and will cause the user device 150 to transmit itscurrent location and/or presence status, in step 1910. Again, the timerwill reset. It is noted that, in certain embodiments, no location orpresence change will be transmitted to the remote server until the timerexpires, even if a change is detected during the countdown. Further, inother embodiments, the remote device will send a location or presenceinformation to the server upon expiration of the timer, regardless ofwhether there has been a change or a determination of a change since theprevious transmission.

FIG. 19B is a flowchart illustrating alternate use of a timer ticksystem according to an embodiment of the present invention. At a step1920, the remote device 150 activates or otherwise registers with theremote server 152, and begins location and/or presence monitoring. Inresponse, at a step 1922, the remote server 152 activates its timer1802. Next, in a step 1924, in certain embodiments, the remote device150 determines if there has been a presence or location change prior toexpiration of the timer. If so, then in step 1930, the remote device 150sends an update to the remote server 152. Otherwise, in a step 1926, thetimer expires. At a step 1928, the remote server 152 then sends a timertick or “Here I am” signal to the remote device 150. The remote device150 receives the signal and, in response, can check and send the currentlocation and/or presence status. If no response is received, the remoteserver 152 can update the user's presence status to “unavailable” or“unknown.” Again, in certain embodiments, the remote user will notupdate the remote server 152 until reception of the timer tick signal,even if there is a change in status prior to receiving it.

FIG. 19C is a flowchart illustrating another alternate use of a timertick system according to an embodiment of the present invention. Asshown, at a step 1950, the remote device 150 activates or otherwiseregisters with the remote server 152, and begins location and/orpresence monitoring. In response, at a step 1952, the remote server 152activates its timer 1802. At a step 1954, the timer 1802 can expire.When it does, the remote server 152 sends a timer tick signal, in a step1956. In a step 1958, the remote device 150 can send a response tick. Ifno response is received, the remote server 152 can update the user'spresence status to “unavailable” or “unknown.” In a step 1960, theremote device 150 can detect a change in presence or location status. Ifit does, then in step 1962, the remote unit 150 will send an update instatus to the remote server 152. Otherwise, it will continue to monitor.The timer 1802 can be reset upon expiration and upon reception ofupdated status information. It is noted that, in other embodiments, thecurrent status will be transmitted regardless of whether there has beendetermined to be a change.

Loss of Signal

In certain embodiments of the present invention, it may be the case thata global positioning signal is not received when a user is inside abuilding. In such a case, the system according to embodiments of thepresent invention may determine that the user is in a building at anaddress associated with a position where the signal faded or was lost.

This is illustrated schematically in FIG. 20A. As shown at 2000 a, auser is normally able to receive both GPS signals and cell phone signals2011 a. At position 2000 b, the user may be within a building and thusreceive only cell phone signals 2011 b. When the user exits thebuilding, at 2000 c, the user again receives both GPS and cell phonesignals 2011 c. In operation, the system may assign an address to theuser when the user is tracked to a point where the GPS signal is lost.For example, at perimeter 2002, the GPS signal may be lost or fall belowa predetermined threshold. In this case, the user may be “assigned” alocation closest to the one where the signal was lost. Alternatively,the position the signal was lost may be compared to a known address, andthe user may be assigned that address over the period during which thesignal is lost. Further, when the user is deemed to be at such alocation, contact information may also be updated. Thus, when the signalis lost at 2002, the user's contact information may be switched from hiscell phone to an office telephone number.

It is noted that, while in some cases it may be desirable to updatelocation and presence each time the signal is lost and regained, inother cases the location at which the signal is lost may be a subset ofanother position related to presence. This is illustrated in FIG. 20B.Shown in FIG. 20B is an area 2050 that may be associated with a single“location” and presence indicia. For example, the area 2050 may be thecity of Munich, and the location can simply be “Munich,” with anassociated contact telephone number, such as a GSM cell phone. In thiscase, it would not necessarily be required to continually update thelocation or presence, since the user's presence status will not change.

For example, at position 2052 a, the user is within the area 2050 andhence in “Munich.” At position 2052 b, the user may be within a buildingin Munich, where his GPS signal fails. The user's location, Munich, neednot necessarily be changed to a more specific one (i.e., the specificaddress of the building), because the user is still within area 2050.Even when the user's GPS signal is restored at 2052 c, the location neednot be updated. Only when the user leaves area 2052 d, e.g., to returnhome, would the location be updated.

A flowchart illustrating operation of such an embodiment of the presentinvention is shown in FIG. 21. At a step 2102, the system monitors theuser's current location. At a step 2104, the system detects loss of theGPS signal. For example, the remote device 150 can determine that thesignal has fallen below a predetermined threshold. At step 2106, thesystem checks to see if a new rule is to be implemented in response tothe loss of signal. That is, depending on the embodiment, the remotedevice 150 can check its rules database, or it can simply send a signalto the remote server 152 advising of the loss of the signal. If a newrule is to be implemented, then the user's location and/or presence areupdated according to the new rule. Otherwise, he current rule ismaintained, in step 2112. Once the new rule has been implemented, thesystem can detect reception of the GPS signal, i.e., once the userleaves the building, in a step 2110. Again, the remote device 150 candetect if the GPS signal exceeds the threshold. The system will monitorto determine if the received signal indicates that a new rule should beimplemented, as shown instep 2114. If so, then in step 2116, the newlocation rule is implemented. If not, then in step 2118, the old one ismaintained.

Hysteresis

As discussed above, embodiments of the present invention can be used todefine a user presence status based on user speed. For example, a userspeed of, say 15 miles per hour or greater can be associated with apresence status of “In car” and an availability of “cell phone.” As canbe appreciated, however, particularly when driving in large cities andwhen stopped at a light or in traffic, the user's speed may not beconstantly above 15 miles per hour. Consequently, to prevent continuoustoggling, a hysteresis time threshold can also be set and transferred tothe remote device.

That is, in certain embodiments of the present invention, when a user is“In Car,” the appropriate system component must determine that the userhas been traveling at a speed below the threshold for a predeterminedperiod prior to deciding that his presence status has changed.

For example, FIG. 22 is a flowchart illustrating operation of anembodiment of the present invention. At a step 2202, the system detectsa user device speed above a threshold T. In certain embodiments, thethreshold can be 15 miles per hour and be user-settable, in a mannersimilar to that discussed above. At a step 2204, the user's presencestatus is set to “In car.” At a step 2206, the remote user is detectedas having a speed less than the threshold T. At a step 2208, the systemdevice responsible for setting user status starts a hysteresis timer. Ifthe speed is still less than the threshold upon expiration of the timer,as determined in step 2210, then in step 2212, the user's status can bechanged. For example, prior to getting in the car, the user's locationand status could have been “In city” and “At lunch,” respectively. Whenthe user is detected as moving at speed, the presence status can beupdated to “In car.” When the user is detected as moving below thethreshold for a predetermined period, the presence status can be updatedto “At lunch,” once more.

It is noted that similar hysteresis timers/thresholds can be provided inassociation with any of the location-status rules. Such hysteresistimers may be particularly useful in situations in which the GPS signalhas been lost due to the user entering a building. To prevent thetoggling that would result if the user is, say, waiting at the entranceto the building, moving inside and outside GPS range, hysteresis timersmay be provided.

This is illustrated more particularly with reference to the flowchart ofFIG. 23. As shown, in a step 2302, the system detects a loss of GPSsignal. For example, the remote device 150's GPS controller can detectthat the GPS signal is below a predetermined threshold. At a step 2304,the remote device 150 starts a hysteresis timer. If there is still nosignal upon expiration of the hysteresis timer, as shown in step 2306,then in step 2308, the remote device 150 updates the user's presencestatus. Otherwise, the system waits for the loss of signal again. Asimilar process is used if the user moves from a state of “No signal” to“Signal.”

Third-Party Monitoring

According to an embodiment of the present invention, an improvedthird-party location monitoring device is provided. Briefly, in additionto providing the presence capabilities as described above, a remotedevice according to embodiments of the present invention may be affixedto an object, person, or pet, and set to trigger an alarm if it departsfrom a user-programmed range. A graphical user interface is provided forsetting the range. Rules, presence, location and alarm updates may betransmitted in a manner similar to that discussed above, i.e.,wirelessly and/or using e-mail or text messaging techniques.

One embodiment of a remote unit in accordance with the present inventionis shown with reference to FIG. 24. In the embodiment illustrated, theremote unit 2-150 may be removeably affixed to an object or person orpet, such as via a lock, etc. As shown, the remote unit 2-150 includesGPS receiver 504 and controller 502. In the embodiment illustrated, theremote unit 2-150 may be affixed to a person or pet via belt 2402 toprovide a monitor with presence and location information related to themonitored user. In addition, in certain embodiments, an audible alarm2404 may be provided.

Operation of this embodiment of the present invention is shown withreference to FIG. 25. Shown is remote unit 2-150 and exemplary sitesHome 2500 and School 2502. A boundary or perimeter 2504 is defined by abase or home user, as will be explained in greater detail below, and isuploaded to the remote device 2-150. The remote unit 2-150 is trackedwithin the area defined by boundary 2504, in a manner similar to thatdiscussed above; presence information, such as contact information(e.g., a school telephone number), may be provided. If the device exitsthe region or crosses the boundary, an alarm will be sent to anadministration device such as a base or home user. As will be explainedin greater detail below, the user may also define day of week and timeof time associations with the boundary 2504.

A system for programming the remote unit 2-150 is shown in FIG. 26. Ingeneral, the system of FIG. 26 is similar to that of FIG. 1, but may bemore suitable for a home user. As shown, the system includes anadministration device such as a server 104/152 (for convenience,functions of the servers 104,152 are shown in a single unit), as well asa client computer 2-122, with software 2-124 to program location andtime ranges, as well as presence and contact information. The computer2-122 may be equipped with a modem or other network interface device2602 for communicating with the server 104/152. As shown, the modem 2602may be implemented as a landline modem or a wireless modem.

In operation, the client computer 2-122 programs location and/ortime-date boundaries, which are uploaded to the server 104/152 via modem2602. The server 104/152 then “calls” the cellular phone number of theremote unit 2-150 and uploads the location parameters and can associatepresence information, as well. In turn, the remote unit 2-150periodically receives GPS signals and transmits the associatedcoordinates to the server 104/152, which can then send these to theclient 2-122. Alternatively, the remote unit 2-150 itself can performthe location compares and transmit to the client 2-122 when it detectsit is outside the defined boundaries.

It is noted that, in alternate embodiments, the client computer 2-122could perform all server-related functions. Further, it is noted thatthe location alarm could be sent to any desired location, i.e., a usercellular telephone not directly associated with the client computer2-122. Thus, the figures are exemplary only.

FIG. 27 illustrates an exemplary graphical user interface for settinglocation and time parameters. For example, 2702 illustrates a mappingwindow for defining the boundary 2504 and one or more place locations2500, 2502. In operation, a user could draw the boundary on the desiredmap, and define individual addresses 2500, 2502 for special treatment.For example, a second window 2704 for entering day 2708, time 2710, andlocation (e.g., address) 2712 parameters is also shown.

Turning now to FIG. 28, a flowchart illustrating operation of anembodiment of the present invention is shown. In a step 2802, the usercan program in the location parameters. At step 2804, the user canprogram in associated date and time parameters. The received parameterscan be maintained in a database in association with a deviceidentification at the client computer, the server, or the remote unititself, in a manner similar to that discussed above. The parameters maybe sent to the remote unit 2-150 via the modem by dialing an associatedcell phone number. In step 2806, the system then monitors the location.

Turning now to FIG. 29, a flowchart illustrating operation of anembodiment of the present invention is shown. At step 2902, the remoteunit 2-150 receives position signals, such as GPS signals. At step 2904,the received position signal is compared with the database. As notedabove, this may be done either at the remote unit itself, by the server,or by the client computer. If the remote unit 2-150 is determined to beoutside the range, as determined at step 2906, then in step 2908, analarm is signaled. Otherwise, at step 2910, the system continues tomonitor the location.

Secure Monitoring

In addition, a tracking system such as described above may be equippedto allow a monitored person to request a boundary or schedule change.Such a system may be used, for example, by a parolee and parole officer.Again, rules, presence, location and alarm updates may be transmitted ina manner similar to that discussed above.

Such a system 3000 is shown in FIG. 30. In the embodiment illustrated,the system 3000 includes a remote security device 30-150 and server30-152. The remote security device 30-150 and server 30-152 maycommunicate, as in the above embodiments, via the Internet or cellularor PCS networks. In addition, the system includes a user computer, suchas a personal computer 3004, which couples via the Internet to a monitoragent 3008, who is also capable of communicating with the monitor server30-152. The monitoring server includes database 3010, which isaccessible from monitor agent, typically a secure connection.

In operation, the security device 30-150 is programmed with apredetermined user schedule and location boundaries. The security device30-150 will send an alarm to the monitoring agent 3008 if the userviolates those boundaries or deviates from the schedule. In certainembodiments, the alarm may additionally be an audio alarm. Such an alarmcould sound when the user exits the permitted area, and increase involume over a predetermined period or range of the boundary until itachieves a maximum, as will be explained in greater detail below.

In addition, as will be explained in greater detail below, the user mayrequest a temporary deviation from the schedule. For example, if theuser must travel to a location not on the schedule or within theboundaries, he can use computer 3004 to request a temporary change inthe boundary. The request is transmitted to the monitoring agent 3008,who can deny or grant the request. If the request is granted, thedatabase 3010 is updated.

The actual monitoring of the device 30-150 and communicating updates maybe accomplished in a manner similar to that discussed above. Theexception request, however, may be made using e-mail and/or a secureInternet host web site Internet such that the user can log in to thehost and transmit the request. For example, FIG. 31 illustrates anexemplary secure web page request window 3100. As shown, the windowincludes a current schedule 3102 and a modification request 3104. It isnoted that such a modification request web page may have differentformats and employ suitable scripting to ensure security. The figure isexemplary only. Alternatively, the user can compose a suitable e-mail ortext message including the necessary identification and re-schedulinginformation.

In either case, the request is received at the monitoring agent 3108,such as a parole officer. The monitoring agent 3108 can himself log into the supervising server 31-152 to accept or reject the request. If therequest is accepted, the monitoring agent 3108 can update the databaseand transmit the update to the remote unit. For example, the update maybe transmitted to the remote unit 31-150 using the cellular telephonenetwork in a manner similar to that described above.

Turning now to FIG. 32, a flowchart illustrating operation of anembodiment of the present invention is shown. In a step 3202, themonitored user can access a monitor web site, or otherwise compose amodification request. In a step 3204, the request can be delivered tothe monitoring agent. If the request is granted, in a step 3206, thenthe update to the boundaries/schedule is transmitted to the securitydevice 31-150. Otherwise, the monitoring agent can respond, in a step3210, via the web or an e-mail or other communication method.

Intermediate and Audio Alarm

As noted above, the remote device can be equipped with an audible alarmas well as the transmission alarm, which can vary depending on theamount of time or the distance the user has violated the boundarycondition. As shown in FIG. 33, the volume of the audible alarm 3350 canincrease with distance or time, until it a threshold 3352 of distance ortime is reached. At this time, the volume can plateau at a maximum level3354.

Shown in FIG. 34 is a map that may correspond to the volume graph ofFIG. 33. Shown is a user 3400, a warning boundary 3402, and a boundary3404. In operation, the system may detect the user crossing the warningboundary 3402, which may correspond to point d1 on the graph of FIG. 33.As the user proceeds to boundary 3404, the volume increases; theboundary 3404 may correspond to the point df on graph of FIG. 33. Atthis point, the volume is at a maximum. Similarly, as noted above, thevolume alarm may be triggered based on time after crossing eitherwarning boundary 3402 or boundary 3404.

Operation of this embodiment is shown with reference to the flowchart ofFIG. 35. As shown, in step 3502, the remote security unit 31-150monitors the user's location. If the user is inside the designated area,as determined in step 3504, the system will continue to monitor. If theuser is outside the designated area, then in step 3506, the device31-150 may sound an audible alarm or send an alert to the monitoringstation 31-152. As noted above, in certain embodiments, the user may begiven a predetermined time to return to within the designated boundaryprior to sounding the alarm.

A flowchart illustrating operation of another embodiment of the presentinvention is shown in FIG. 36. In step 3602, the device 31-150 detectsit is outside the prescribed area. At 3604, a timer is started. This maybe either on-board or associated with the remote server(s). At 3606, thetimer may expire. The system checks if the user is still outside thedesignated area, in step 3608. If not, the system will simply continuemonitoring, in step 3612. Otherwise, at step 3610, the system can soundthe alarm, either at a maximum level, or a ramp up level.

The invention described in the above detailed description is notintended to be limited to the specific form set forth herein, but isintended to cover such alternatives, modifications and equivalents ascan reasonably be included within the spirit and scope of the appendedclaims. For example, while described primarily with reference to globalpositioning signals, alternative methods for determining device locationmay be used. These can include, for instance, use of cell locationsignals within the cellular network.

1. A telecommunications system, comprising: a plurality of remoteclients including a positioning controller and a communicationscontroller, said positioning controller receiving position informationand said communications controller communicating said positioninformation; and a server including a coordinating controller formaintaining a database of location-presence rules for remote clientsthat are being tracked; wherein said location-presence rules areuser-configurable from a network client; wherein said location-presencerules define user availability on a plurality of user devices associatedwith the user; and wherein said location-presence rules define one ormore contexts with regard to a predetermined geographic boundary anddefine particular ones of said plurality of remote clients by which theuser may be contacted.
 2. A telecommunications system in accordance withclaim 1, wherein said positioning controller receives global positioningnetwork signals for determining a position of an associated networkclient.
 3. A telecommunications system in accordance with claim 2,wherein said communications controller comprises a cellular networkcontroller for transmitting on a cellular telephone network to saidserver.
 4. A telecommunications system in accordance with claim 1,wherein said network clients include one or more graphical userinterfaces (GUI) for inputting geographical information, presencestatus, and contact information via a mapping feature.
 5. Atelecommunications system in accordance with claim 1, wherein saidremote clients receive said location-presence rules from said server. 6.A telecommunications system in accordance with claim 1, wherein saidremote clients transmit current location information to said server. 7.A telecommunications server, comprising: a presence control unit adaptedto receive and maintain presence information for a plurality of users;and a location control unit adapted to receive and maintain locationinformation for said plurality of users, said location informationcorrelated with said presence information, said location informationbeing received from remote users having positioning controllers forreceiving location information and communication controllers fortransmitting said location information to said server via a wirelesscommunication network; wherein presence and location correlation rulesare received from one or more network clients operably coupled to saidserver and associated with said remote users and wherein said locationand presence correlation rules define user availability and a pluralityof contexts on each of a plurality of user devices associated with aparticular user with regard to a predetermined geographic boundary.
 8. Atelecommunications server in accordance with claim 7, wherein saidnetwork clients comprise one or more computers with graphical userinterfaces including mapping features for setting said presence andlocation correlation rules.
 9. A telecommunications server in accordancewith claim 8, wherein said presence and location correlation rulescomprise setting location, presence, and contact rules.
 10. Atelecommunications server in accordance with claim 9, wherein saidlocation information is received via a global positioning network.
 11. Atelecommunications server in accordance with claim 10, wherein saidlocation information is transmitted via a cellular telephone network.12. A telecommunications method, comprising: receiving one or more userpositioning and presence correlation rules at a server, whereinpositioning information is received from remote users having positioningcontrollers for receiving location information and communicationcontrollers for transmitting said location information to said servervia a wireless communication network; and transmitting said one or morepositioning and presence correlation rules to at least one of saidremote users; and wherein said positioning and presence correlationrules define user availability and one or more contexts on a pluralityof user devices associated with a particular user with regard to apredetermined geographic boundary.
 13. A telecommunications method inaccordance with claim 12, further comprising: receiving positioningupdates at said remote user; and transmitting presence updates to viasaid server as specified in said one or more positioning and presencecorrelation rules.
 14. A telecommunications method in accordance withclaim 13, wherein said receiving one or more user positioning andpresence correlation rules comprises receiving at said server one ormore rules set via a network interface device operably coupled to saidone or more local controllers.
 15. A telecommunications method inaccordance with claim 14, wherein said receiving positioning updatescomprises receiving one or more signals from a global positioningnetwork.
 16. A telecommunications method in accordance with claim 15,wherein said wireless network comprises a cellular telephone network.17. A telecommunications method in accordance with claim 15, whereinsaid wireless network comprises a personal communication service (PCS)network.
 18. A graphical user interface for setting one or more locationand presence correlation parameters for use by remote network deviceshaving positioning controllers for receiving positioning signals andcommunication controllers for transmitting said positioning signals to aserver; wherein said positioning signals comprise global positioningsystem signals; and wherein the location and presence correlationparameters define an availability and one or more contexts of a user ata plurality of devices at a plurality of locations defined bypredetermined boundaries.